Harden PR assignment workflow against untrusted workflow_run artifacts#4
Open
theinfosecguy wants to merge 1 commit intolinkedin:masterfrom
Open
Conversation
Restrict dependency artifact generation and downstream reviewer assignment to same-repository pull requests so privileged workflow_run jobs cannot consume artifacts from fork PR code. Made-with: Cursor
8e164d6 to
99f01f5
Compare
ChrisCarini
approved these changes
Mar 31, 2026
Member
ChrisCarini
left a comment
There was a problem hiding this comment.
LGTM! Consider contributing this upstream, too!
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
PR-assignment-deps.ymlto pull requests whose head repository matches the base repository.PR-assignment.ymlso privileged reviewer assignment does not process artifacts from fork-originated workflow runs.Testing Done